Document the unreleased changes for 0.10.0 - #68

Description

Write the Unreleased notes for the planned 0.10.0 release from fork PRs #55–#67, following #53's documentation-only approach. Group by user impact and separate source changes, PR-head CI evidence and pending combined packaged validation.

Scope

• CHANGELOG.md: Added, Changed, Fixed and Security; fourth-engine llama.cpp lifecycle/routing/model management, reachability, ordered IPC, engine cleanup and port behavior.
• docs/release-readiness.mdx: included changes, linked CI results for every PR, Live validation (pending) checklist, open decisions and held items.
• docs/known-issues.mdx: explicit model/platform/picker limitations, remaining roaming boundary, cache residue/refresh behavior and Windows runtime limits.

No runtime code, versions, desktop/package.json, README release lines or released changelog entries changed. Stale oMLX launcher and unpinned Ollama issues were already removed by #56; no TestModelsHTTPEnrichment flake or saved-fallback issue was listed in known issues. Historical readiness follow-ups now identify their source fixes instead of treating them as current defects.

Classification: same-UUID discovery availability (#66) and checksum-pinned fresh Ollama installs (#56) are Security. Lifecycle/process cleanup, IPC stalls, model identity/cache errors and fallback-port correctness are Fixed. Peer roaming is Changed; the running-port note is Changed. No exploit details or new performance claims.

Validation

macOS arm64, isolated /tmp/pair-work/changelog-0100 based on origin/main 877e99f:

• Read Update unreleased notes and packaged-app validation #53 and its merge diff, all PR descriptions Let paired machines reconnect after address changes #55–Show temporary engine port fallbacks in settings #67 and relevant code/manifests/tests.
• node scripts/spdx-headers.mjs: 1,577 checked; zero missing, review or unclassified.
• git diff --check: passed.
• Read Makefile and package scripts and searched for documentation lint/link tooling: no dedicated docs-site lint/link check is configured.
• Dependency-free local check: only the three intended files changed, the entire changelog from 0.9.0 onward is byte-identical, exclusion scan clean, all 33 relative documentation link targets exist.
• No local live engine, app installation, GUI or cross-process test run; combined live validation is explicitly pending. PR-specific older smoke evidence is not recast as final-artifact certification.

Final head 684e3cb419e0bc5bdeeea51420fb05ec64db291f: CI run 42466489986, attempt 2, completed successfully with all six jobs passing: SPDX, Desktop, Go modules on Linux/macOS, and cross-process on Linux/macOS. Verified the exact head SHA and all six job conclusions through the GitHub API.

Attempt 1's Desktop job failed after repeated HTTP 504 responses downloading Electron; two test files could not load the missing binary (980 other tests passed). Retried only that failed job on the unchanged head after the other five jobs passed. The retry passed; no code/dependency/workflow workaround was made.

Downloaded the successful cross-process-ubuntu-latest artifact from this same head with gh run download into the new empty directory /tmp/pair-review/changelog-0100-linux.PeNS5I; python3 -I ~/.pair-review/scripts/noskip.py /tmp/pair-review/changelog-0100-linux.PeNS5I/cross-process.jsonl returned {'pass': 127} [], exit 0: zero skips/failures. Repeated the checker after the Desktop retry completed. A separate all-event audit also found zero skip/fail events and a passing package terminal event. macOS job success is not a claim that its multicast-dependent cases ran.

New cross-document anchors and exact pending/held wording were checked after commit. The clean implementation worktree has been removed; the signed-off commit is pushed.

Risk

Documentation accuracy/classification only. llama.cpp remains macOS arm64-only, ad-hoc signed and unnotarized, with a single-file Q4_K_M catalog and no peer startup-model picker. Windows runtime remains untested. Existing published release and artifact claims are unchanged; no release is cut by this PR.

Checklist

• I have read the Contributing Guidelines.
• Every commit is signed off (git commit -s), certifying the Developer Certificate of Origin.
• Documentation-only checks cover this change; no runtime tests added.
• Relevant documentation is updated.
• I checked the diff, changed filenames and commit messages for private data, generated artifacts and unrelated changes.
• I recorded validation commands and results above, including final-head six-job CI and the Linux zero-skip artifact audit.
• Component versions reviewed: no bump applies to a documentation-only change; release preparation is separate.